Two of These Are the Automation. The Other Ten Are the Workers.
Twelve free AI tools in one graphic, and they are not the same kind of thing at all.
Two of them are the actual automation. Zapier and Make connect your apps, so when something happens in one, something else happens in another. No code required.
The other ten are the workers those automations can call on: ChatGPT, Claude, Perplexity and Gemini for writing and research; Gamma for slides, Canva for design, Runway for video, ElevenLabs for voice; Notion AI and Google Sheets for organising. Powerful, and none of them connect anything on their own.
Getting that distinction right is the difference between building a system and collecting logins.
Trigger, flow, worker: how it actually runs
“Work while you sleep” is not magic and it is not one product. It is a chain of five steps.
| 1. Trigger → | 2. Flow → | 3. Worker → | 4. Destination → | 5. You check |
|---|---|---|---|---|
| Something happened A new row, form, email or file |
The connector notices Zapier or Make, no code |
The AI does the job Write, summarise, design, voice |
The result lands somewhere A sheet, a doc, a draft, a folder |
Before anything is public The step people skip, and regret |
| A video goes live | Make picks up the RSS entry | Claude drafts five short posts from the description | They appear as drafts in your notes app | You edit and post the two that are good |
A worker without a flow is a tab you open by hand. A flow without a worker just moves data from one place to another. Put them together and the boring half of a task disappears – the half that was you carrying information between apps, which we mapped in the job disappearing is carrying.
The twelve, by role
Here is the full set, with each tool’s place in the chain.
| Role | Tool | What the card says it does | Its job in a flow |
|---|---|---|---|
| Connector | Zapier | Connects thousands of apps, no code | Starts and runs the flow |
| Connector | Make | Visual automation flows for multi-step tasks | Starts and runs the flow |
| Worker | ChatGPT | Versatile assistant for writing and research | Drafts, rewrites, summarises |
| Worker | Claude | Long documents and careful reasoning | Handles the big pasted transcript |
| Worker | Perplexity | Research with sources | Checks a claim before you repeat it |
| Worker | Google Gemini | Multimodal, built into Google tools | Works where your docs already live |
| Worker | Gamma | Turns a prompt into slides or a page | Builds the deck from an outline |
| Worker | Canva AI | Visuals, decks and brand assets | Makes the graphic from the text |
| Worker | Runway | Generates and edits video from prompts | Produces b-roll without an editor |
| Worker | ElevenLabs | Studio-quality voice from text | Narrates the cut |
| Organiser | Notion AI | Your workspace as a thinking partner | Holds the output where you will find it |
| Organiser | Google Sheets | Free spreadsheets, formulas and clean-up | The record every flow writes to |
The two organisers are easy to underrate. Every flow needs somewhere to put its output where you will actually see it – a sheet, a page, a folder. Automations that deliver into a channel nobody checks are worse than no automation, because they create work quietly.
The post this came from
Watch the reel
Twelve free AI automation tools, with the free-plan note on every one. Posted on the BANI Academy page.
Five boring tasks worth automating first
The advice in the reel is the right advice: start with one boring task you repeat every week. Here are five that fit a channel, with the trigger and the worker already chosen.
| The boring task | Trigger | What the worker does | Where it lands | How often |
|---|---|---|---|---|
| A video goes live | New entry in your channel feed | A writing worker drafts five short posts | Drafts in your notes app | Every upload |
| Monthly numbers | A date, once a month | A sheet collects the figures, a worker writes three sentences on what moved | A row in the record | Monthly |
| Comment questions | A new comment matching a keyword | A worker drafts a reply for you to approve | A draft list, never auto-posted | Daily |
| Sponsor enquiry | A new email or form entry | A worker summarises it and drafts a reply | A labelled folder and a draft | Rarely, but urgent |
| Research notes | A new link saved to a folder | A research worker summarises it with sources | The project where you write | Weekly |
Notice that none of these publishes anything. Every one ends in a draft, a row or a folder that you look at. That is deliberate: automation is excellent at fetching, formatting and preparing, and poor at deciding – the same division we argued for in agents research, you decide.
The third row in particular should never post by itself. A generated reply that misreads a viewer’s question costs more goodwill than the two minutes it saved, and comments are where a small channel earns its regulars.
Why people buy the workers and never build the flow
There is a reason the ten workers get all the attention and the two connectors get almost none. A worker gives you something to look at in thirty seconds: a draft, an image, a voice clip. A connector gives you nothing visible at all until it has been set up, and its best possible outcome is that you stop noticing a task you used to do.
So people accumulate workers. Four assistants, two image tools, a voice tool, a slides tool – and every one of them still opened by hand, pasted into by hand, and exported from by hand. The tools got better; the week did not change, because nothing was connected.
The fix is not more restraint about trying tools. It is spending one afternoon on the unglamorous layer, once. After that the same workers you already have start being called automatically, and the difference shows up as an ordinary week with one less chore in it – which is exactly what makes it easy to underrate and worth doing anyway.
Three things to check before you build
The free-plan limits. Every tool on the card has a free plan, and the card says so honestly. What free plans meter is usually the number of runs per month on the automation side, and the number of generations on the worker side. A flow that fires on every comment will find that ceiling within days, so count the expected runs before you switch it on – the wider version of that arithmetic is in the limit is the price.
The access you are granting. A connector sits between your accounts by design, which is exactly what makes it useful and what makes it worth being careful about. Connect the narrowest thing that works, start read-only, and treat anything the assistant reads as data rather than instructions – the three rules in stop pasting.
Whether you will notice a silent failure. Automations rarely announce that they stopped. They just stop, and three weeks later you find an empty sheet. Give every flow a destination you open weekly, and one obvious sign of life – a dated row, a count, a message. This is the observability layer that companies buy products for and one person covers with a habit, as in the enterprise AI stack, shrunk to one person.
Frequently asked questions
Do I need both Zapier and Make?
No. Pick one. They do the same job; one is quicker to start with, the other gives more control over multi-step flows.
Are the free plans enough?
For one or two flows running a few times a week, usually yes. Free automation plans count tasks or operations per month, so check the number before you build.
What access do these tools need?
Whatever apps you connect. Start with read-only where the tool offers it, and connect one folder or one sheet rather than a whole account.
What if the flow breaks?
It will, eventually. That is why the destination should be somewhere you look at weekly – silence is not the same as success.
Build one flow this week
Write down the task you repeated most times last month. Name its trigger, pick one connector, pick one worker, and choose a destination you already open. Build that single flow, run it manually twice to see what it produces, then let it run on its own for a fortnight – with you still reading the output before anything goes public.
One flow that runs quietly beats twelve accounts you signed up for. And when it does save you an hour a week, you will know exactly which hour it was, because you counted it before you started.
Learning a lot does not make anyone good. Doing a lot does.
If you want the structure that turns that into a habit, that is what our free challenge is built for: no barrier to entry, a genuine commitment to action, and a refundable commitment fee you get back when you finish. You are not paying for the knowledge. You are betting on yourself finishing, and we hold the stake.
Which boring task would you automate first? Tell us in the comments on the original reel.
For more on building channels for English-speaking audiences, that is what we work on at mmoyoutube.com.
One Comment